ALPHAbook[TM]_1_____________________________________ Firmware Update Procedures Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ First Printing, February 1996 Revised, May 1996 Revised, September 1996 Revised, December 1996 Revised, March 1997 Revised, August 1997 Revised, October 1997 Revised, January 1998 Revised, June 1998 Revised, September 1998 Revised, March, 1999 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. Copyright © Digital Equipment Corporation, 1996, 1997, 1998, 1999. All Rights Reserved. COMPAQ, the Compaq logo and the Digital logo Registered in U.S. Patent and Trademark Office. Alpha, Bookreader, DEC, DECchip, DECpc, DECwindows, DEC VET, DIGITAL, InfoServer, OpenVMS, RRD43, RZ, TURBOchannel, ULTRIX, VAX, VAX DOCUMENT, and VMS are trademarks of Compaq Computer Corporation. ALPHAbook is a trademark of Digital Equipment Corporation, licensed exclusively to Tadpole Technology, Inc. PostScript is a registered trademark of Adobe Systems, Inc. Windows NT is a trademark of Microsoft, Inc. Motif is a registered trademark of the Open Software Foundation, Inc., licensed by DIGITAL. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. ThisNdocumenthwasqprepareddusingbVAXiDOCUMENTaVersion 2.1. generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference when operated in a commercial environment. Operation of this equipment in a residential area may cause interference, in which case the user at his own expense may be required to take measures to correct the interference. _________________________________________________________________ Contents Preface................................................... v 1 ALPHAbook 1 Firmware Update Procedure 1.1 Updating System Firmware...................... 1-1 1.1.1 System Firmware........................... 1-1 1.1.2 Update Utility............................ 1-1 1.2 Updating an OpenVMS System.................... 1-1 1.2.1 Step 1: Turn the System On................ 1-1 1.2.2 Step 2: Determine the Device ID of the CD-ROM Drive.............................. 1-2 1.2.3 Step 3: Load the Firmware Update Utility Compact Disc.............................. 1-2 1.2.4 Step 4: Boot the Firmware Utility Disk.... 1-2 1.2.5 Step 5: Update the System................. 1-4 1.2.6 Step 6: Verify ROM Update was successful................................ 1-4 1.2.7 Step 7: Exit from the Firmware Update Utility................................... 1-4 2 Network and InfoServer Upgrades 2.1 MOP Network Upgrade........................... 2-1 2.1.1 Step 1: Load the Firmware Update Utility Compact Disc.............................. 2-3 2.1.2 Step 2a: VMS File Copy Instructions....... 2-3 2.1.3 Step 2b: ULTRIX or DIGITAL UNIX File Copy Instructions.............................. 2-3 2.1.4 Step 3: Set Up Host....................... 2-3 2.1.5 Step 4: Boot the Firmware Update Utility................................... 2-4 2.1.6 Step 5: Perform Update.................... 2-5 2.2 BOOTP Network Upgrade......................... 2-6 iii 2.2.1 Step 1: Mount the Firmware Update Utility CD-ROM.................................... 2-6 2.2.2 Step 2: Modify or Create the Client Database in the /etc/bootptab File........ 2-6 2.2.3 Step 3: Invoke bootpd and tftpd daemons... 2-6 2.2.4 Step 4: Enter the Following Command....... 2-7 2.2.5 Step 5: Perform Update and System Initialization............................ 2-7 2.3 InfoServer Upgrade............................ 2-7 2.3.1 Step 1: Enter the Following Command....... 2-7 2.3.2 Step 2: Perform Update and System Initialization............................ 2-8 3 ALPHAbook 1 Firmware Information 3.1 New Features.................................. 3-1 3.2 SRM Firmware Limitations...................... 3-1 Tables 1 ALPHAbook 1............................... viii 2-1 Updating System Firmware.................. 2-1 iv _________________________________________________________________ Preface Purpose of This Guide This guide is intended for all managers of the ALPHAbook 1 systems. This guide describes how to update the system's firmware using the Firmware Update Utility. Purpose and Responsibility of the Firmware Update Utility The Firmware Update Utility has been developed to allow the owners of existing and new ALPHAbook 1 systems to maintain firmware on their systems. Firmware provides a number of basic functions on your system, including operating system bootstrap, configuration identification, testing and some basic input/output operations. To assist the owner, who's responsibility it is to perform the update, a simple and user friendly interface is provided as part of the Firmware Update Utility. This program should be executed as directed by the release notes whenever new software is purchased or as directed by Digital Equipment Corporation. Conventions The following conventions are used in this guide: ___________________________________________________________ Convention_______Description_______________________________ A key name in a box indicates that you press a named key on the keyboard. v ___________________________________________________________ Convention_______Description_______________________________ A sequence such as indicates that you must hold down the key labeled Ctrl while you press another key. show config This typeface denotes commands and command output. Commands are not case-sensitive except where specifically indicated. italics Italicized letters indicate a variable value that you must provide. For example, >>> set variable Caution Cautions provide information to prevent damage to equipment or software. Warning Warnings contain information to prevent _________________personal_injury.__________________________ vi Firmware and Operating System Revisions ________________________ Notes ________________________ Systems that have shipped recently may have firmware revisions at a higher level than is in this kit. The higher level firmware revisions support the revisions of the operating systems that are currently shipping. Some files on the CD-ROM are from previous firmware releases. Systems should not be loaded with older firmware than is presently installed. The system firmware on this CD has a unique revision and is independent of the revision of this firmware kit. ______________________________________________________ Table 1 shows the compatibility between the firmware revisions and revisions of OpenVMS and DIGITAL UNIX. vii Table_1_ALPHAbook_1________________________________________ SRM_Firmware___OpenVMS_________DIGITAL_UNIX________________ v4.7 6.2-1h2,6.2- - 1h3 v4.8 6.2-1h2,6.2- - 1h3, 7.0, 7.1 v4.9 6.2-1h2,6.2- - 1h3, 7.0, 7.1 v5.0 6.2-1h2,6.2- 4.0x 1h3, 7.0, 7.1 v5.1 6.2-1h2,6.2- 4.0x 1h3, 7.0, 7.1 v5.2 6.2-1h2,6.2- 4.0x 1h3, 7.0, 7.1 v5.3 6.2-1h2,6.2- 4.0x 1h3, 7.0, 7.1 v5.4 6.2-1h2,6.2- 4.0x 1h3, 7.0, 7.1, _______________7.2_________________________________________ Associated Documentation These firmware release notes do not describe how to use the console firmware commands nor do they list their error codes. You can find this information about these subjects in the ALPHAbook 1 User Guide document that came with your system. viii Reader Comments DIGITAL welcomes your comments on this or any other manual. You can send your comments to DIGITAL at the following address: Digital Equipment Corporation Shared Engineering Services 129 Parker Street PKO3-2/E30 Maynard, MA 01754-2199 ix 1 _________________________________________________________________ ALPHAbook 1 Firmware Update Procedure This chapter explains how to update the ALPHAbook 1 firmware. Topics are as follows: o Upgrading an OpenVMS system from a CD 1.1 Updating System Firmware 1.1.1 System Firmware The ALPHABook 1 system contains two flashEPROMs, one with DROM (Diagnostic ROM) and SRM console firmware for the OpenVMS operating systems. See Table 1 for compatible firmware and operating system versions. 1.1.2 Update Utility Use the update utility to update the DROM and SRM firmware. The update utility contains three images: the update utility itself, the SRM image, and the DROM image. 1.2 Updating an OpenVMS System Update an OpenVMSsystem as described in the following sections. 1.2.1 Step 1: Turn the System On The following information is displayed (example): ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5. ef.df.ee.ed.ec.eb.....ea.f4.e9.e8.e7.e6.e5. ALPHAbook 1 Console v5.4-1, built on Sep 3 1997 at 13:26:13 >>> ALPHAbook 1 Firmware Update Procedure 1-1 1.2.2 Step 2: Determine the Device ID of the CD-ROM Drive At the console prompt (>>>), enter the show device command. >>>show device dka0.0.0.6.0 DKA0 IBM DVAS-2810 S1B0 dka400.4.0.6.0 DKA400 TOSHIBA CD-ROM XM-4101TA 0064 dva0.0.0.0.1 DVA0 eoa0.0.0.1.1 EOA0 08-00-2B-38-67-6B pka0.7.0.6.0 PKA0 SCSI Bus ID 7 In the example, the CD-ROM drive has a device ID of DKA400. 1.2.3 Step 3: Load the Firmware Update Utility Compact Disc 1. Remove any compact disc that may already be loaded into the CD drive. 2. Load the Firmware Update compact disc into the drive. 1.2.4 Step 4: Boot the Firmware Utility Disk Please see chapter 3, section 3.1, for new features introduced with this version, of the update utility. Boot the system from the update utility disk, using the device ID determined in step 2. The following is an example of booting the ALPHAbook 1 update utility. 1-2 ALPHAbook 1 Firmware Update Procedure >>> b -fl 0,A0 dka400 Bootfile: [alphabook1]ab1_v5_4.exe bootstrap code read in base = 200000, image_start = 0, image_bytes = 7ee00 initializing HWRPB at 2000 initializing page table at 1f2000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5. ef.df.ee.ed.ec.eb.....ea.f4.e9.e8.e7.e5. ALPHAbook 1 Console v5.4-1, built on Sep 3 1997 at 13:26:13 >>>(boot pmem:180000 -flags 0) bootstrap code read in base = 180000, image_start = 0, image_bytes = 800000 initializing HWRPB at 2000 initializing page table at 792000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code *** ALPHAbook 1 -- Firmware Update v5.4 *** Update VERIfy List Show DUmp VERBose NVerbose DEbug NDebug ? Apu-> ALPHAbook 1 Firmware Update Procedure 1-3 1.2.5 Step 5: Update the System Enter update to update the system firmware: Apu-> update APU-I ARE YOU READY TO PROGRAM (SRM) ROM DEVICE ? (Y/N ) y APU-I ERASING (SRM) ROM DEVICE APU-I PROGRAMMING (SRM) ROM DEVICE APU-I VERIFY LOADED (SRM) ROM IMAGE APU-I VERIFY LOADED (SRM) ROM IMAGE DONE APU-I PROGRAMMING (SRM) ROM COMPLETED Apu-> 1.2.6 Step 6: Verify ROM Update was successful Apu-> verify SRM ROM verify successful 1.2.7 Step 7: Exit from the Firmware Update Utility Cycle power on the system. 1-4 ALPHAbook 1 Firmware Update Procedure 2 _________________________________________________________________ Network and InfoServer Upgrades This chapter explains how to perform network updates: o MOP network upgrades o BOOTP network upgrades o InfoServer upgrades 2.1 MOP Network Upgrade ________________________ Note ________________________ You can use a DIGITAL UNIX system to copy the file from the Firmware Update Utility CD-ROM, but MOP is not supported under DIGITAL UNIX. ______________________________________________________ The ALPHAbook 1 system to be updated (target system) must be powered on and at the console prompt (>>>). Table 2-1 lists the steps required to update the firmware on your ALPHAbook 1 system from the network. Table_2-1_Updating_System_Firmware_________________________ Step___Description_________________________________________ 1 Place the Firmware Update Utility compact disc into the CD drive on the host system. 2 If the host is a VMS, ULTRIX, or DIGITAL UNIX system, copy the update file from the Firmware Update Utility compact disc. 3 Set up the host system. (continued on next page) Network and InfoServer Upgrades 2-1 Table_2-1_(Cont.)_Updating_System_Firmware_________________ Step___Description_________________________________________ 4 Enter a network boot command from the target system. 5 Refer to Section 1.2, steps 5-7 to complete update _______procedure.__________________________________________ 2-2 Network and InfoServer Upgrades 2.1.1 Step 1: Load the Firmware Update Utility Compact Disc 1. Remove any compact disc that may already be loaded into the CD drive. 2. Load the Firmware Update compact disc into the drive. 2.1.2 Step 2a: VMS File Copy Instructions If your host system is VMS, copy the file from the Firmware Update Utility compact disc by entering the following commands at the VMS $ prompt. $ mount dka400: update_v53 $ copy dka400:[SYS0.SYSEXE]ab1_v5_4.sys mom$load: 2.1.3 Step 2b: ULTRIX or DIGITAL UNIX File Copy Instructions If your host system is ULTRIX or DIGITAL UNIX, copy the file from the Firmware Update Utility compact disc by entering the following commands at the ULTRIX or DIGITAL UNIX # prompt. # mount -rt cdfs -o noversion /dev/rz4c /mnt # cp /mnt/ALPHABOOK1/AB1_v5_4.EXE /usr/lib/mop/filename 2.1.4 Step 3: Set Up Host Execute the following when updating an ALPHAbook 1 using a VMS host. You must use NCP to define the characteristics of the host and target system. You will need OPER privileges. $ MCR NCP set circ CIRC_NAME state off $ MCR NCP set circ CIRC_NAME serv enabled $ MCR NCP set circ CIRC_NAME state on ________________________ Note ________________________ CIRC_NAME is the logical name of the circuit used by the network. ______________________________________________________ Execute the following only when updating an ALPHAbook 1 system using an ULTRIX host. Please note that MOP is not supported under DIGITAL UNIX. Network and InfoServer Upgrades 2-3 Make sure the mop_mom process is running. If ps aux|grep mop does not show a mop_mom process, then you must start one by issuing the following command as a superuser: # mop_mom 2.1.5 Step 4: Boot the Firmware Update Utility To start the Firmware Update Utility, enter the boot command at the console prompt on the target system. The following command starts a boot process: >>> boot eoa0 -fi filename ________________________ Note ________________________ The filename must be entered exactly as displayed by the ULTRIX host. ______________________________________________________ After the boot process completes, the Firmware Update Utility menu is displayed. Note the Update Utility prompt (APU->). The following is an example of booting the ALPHAbook 1 update utility. bootstrap code read in base = 200000, image_start = 0, image_bytes = 7ee00 initializing HWRPB at 2000 initializing page table at 1f2000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5. ef.df.ee.ed.ec.eb.....ea.f4.e9.e8.e7.e5. ALPHAbook 1 Console v5.4-1, built on Jan 11 1997 at 13:26:13 >>(boot pmem:180000 -flags 0) bootstrap code read in base = 180000, image_start = 0, image_bytes = 800000 initializing HWRPB at 2000 initializing page table at 792000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code *** ALPHAbook 1 -- Firmware Update v5.4 *** 2-4 Network and InfoServer Upgrades Update VERIfy List Show DUmp VERBose NVerbose DEbug NDebug ? Apu-> 2.1.6 Step 5: Perform Update To complete the update procedure of your system, refer to Section 1.2, steps 5-7. Network and InfoServer Upgrades 2-5 2.2 BOOTP Network Upgrade 2.2.1 Step 1: Mount the Firmware Update Utility CD-ROM # mount -rt cdfs -o noversion /dev/rz4c /mnt 2.2.2 Step 2: Modify or Create the Client Database in the /etc/bootptab File :ht::ha=:bf=AB1_v5_ 4.EXE:ip= where: o host_name is the system name in /etc/hosts. o hw_type is the hardware type. Proteon is ht = 4. Ethernet is ht = 1. Regular token-ring (IEEE 802) is ht = 6. o hw_address is the hardware address: use the console command show device. o ip_address is the corresponding Internet protocol address of the system name in /etc/hosts. The following is an example of a bootptab file: bigsox:ht=1:ha=08002b236423:bf=/mnt/ALPHABOOK1/AB1_v5_4.EXE;1:ip=16.182.0.87 2.2.3 Step 3: Invoke bootpd and tftpd daemons o Modify the /etc/inetd.conf file. Uncommon the tftp and bootps process. It should look like the following example: tftp dgram udp wait root /usr/sbin/tftpd tftpd /mnt bootps dgram upd wait root /usr/sbin/bootpd bootpd o Find the process /usr/sbin/inetd daemon: # ps aux | grep ine # kill process# 2-6 Network and InfoServer Upgrades o Restart the inetd daemon: # /usr/sbin/inetd ________________________ Note ________________________ The bootpd and tftp daemon will be removed if the system is rebooted. Refer to the manual pages: bootpd(8) or tftpd(8) for more information. ______________________________________________________ 2.2.4 Step 4: Enter the Following Command Prior to entering the >>> boot eoa0 command, the user must perform the generic bootp setup as described in Section 3.2, SRM Firmware Limitations. 2.2.5 Step 5: Perform Update and System Initialization To complete the update procedure of your system, refer to Section 1.2, steps 5-7. 2.3 InfoServer Upgrade Be certain to: o Insert the compact disc into a CD-ROM reader that is connected to the InfoServer. o The InfoServer kernel must be at a minimum revision of 2.2 and MOP must be enabled on the InfoServer. 2.3.1 Step 1: Enter the Following Command To perform an upgrade using the InfoServer, enter the following command line. The filename must be in uppercase. >>> boot eoa0 -fi AB1_V5_4. Network and InfoServer Upgrades 2-7 bootstrap code read in base = 200000, image_start = 0, image_bytes = 7ee00 initializing HWRPB at 2000 initializing page table at 1f2000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5. ef.df.ee.ed.ec.eb.....ea.f4.e9.e8.e7.e5. ALPHAbook 1 Console v5.4-1, built on Jan 9 1998 at 11:35:13 >>>(boot pmem:180000 -flags 0) bootstrap code read in base = 180000, image_start = 0, image_bytes = 800000 initializing HWRPB at 2000 initializing page table at 792000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code *** ALPHAbook 1 -- Firmware Update v5.4 *** Update VERIfy List Show DUmp VERBose NVerbose DEbug NDebug ? Apu-> 2.3.2 Step 2: Perform Update and System Initialization To complete the update procedure of your system, refer to Section 1.2, steps 5-7. 2-8 Network and InfoServer Upgrades 3 _________________________________________________________________ ALPHAbook 1 Firmware Information This section describes any new features and/or limitations of the present firmware upgrade. 3.1 New Features o Added SRM2ctrl env var 3.2 SRM Firmware Limitations o Should a boot file ``pathname'' be necessary for either MOP or TCP/IP booting, you should enclose the pathname in quotes. for example: >>>boot eoa0 -file "/dir1/dir2/filename" ALPHAbook 1 Firmware Information 3-1